home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
pressgen
/
nwctip.txt
< prev
next >
Wrap
Text File
|
1994-04-08
|
17KB
|
439 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: NetWare Connect Tips
DOCUMENT ID: TID250047
DOCUMENT REVISION: C
DATE: 21MAR94
ALERT STATUS: Yellow
INFORMATION TYPE: Issue
README FOR: NA
NOVELL PRODUCT and VERSION:
NetWare Connect 1.0
ABSTRACT:
This file includes Technical Tips for NetWare Connect.
------------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY
THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT
OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
------------------------------------------------------------------
ISSUE
I. General Connect Tips
A. Everyone with NetWare Connect 1.0 should download
the following from NetWare in NOVLIB, Library 9:
1. The latest modem support file (NWCMOD.EXE).
2. The latest "Maintenance PTF files (currently,
PTF442.EXE and PTF440.EXE).
Please install all three files because they
correct many problems, including installation
problems. These files should be applied before
any trouble shooting is done.
NWCMOD.EXE will be updated periodically.
B. NetWare Connect should not be installed in a
NetWare 4.x server until you have applied the
PTF442 (or PTF439 or PTF440) files.
All registered owners of 8 port or 32 port NetWare
Connect will be sent RunTime NetWare 4.01.
C. Symptom:
You may receive the following error message:
MESSAGE
Error Report, Description: Could not find
license file at specific path. Severity:
Inform-program execution should continue
normally
Cause:
This can happen if NetWare Connect is installed
from the server volume and the server's
AUTOEXEC.BAT or STARTUP.NCF files load the "Remove
DOS" command. This command prevents access to the
floppy disk drives containing the license disk.
Solution:
Delete the "Remove DOS" command from the
AUTOEXEC.BAT and STARTUP.NCF files. Then shut
down and exit the server. Restart NetWare
Connect.
D. Symptom:
With a Digiboard, you may experience framing
errors or abends.
Solution:
If you experience these problems, or others when
using a DigiBoard, call Digiboard (800-344-4273 or
612-943-9020) and get the latest driver from them.
E. Symptom:
A Multiport board may load but no board number 1
may show.
Cause:
The first AIO multi port board should always be
board 0, and the first AIO port should be port 0.
The mapping should look similar to the following:
(DRIVER_NAME,0,0)
where DRIVER_NAME is the currently loaded AIO
driver.
Solution:
On the board driver LOAD line, put NODE=0 for the
first board, NODE=1 for the second board, and so
forth. (Note: The WNIM board neither supports
nor requires a NODE= statement).
Example: load AIODGXI port=200 mem=d0000 node=0.
F. Question:
The LOAD Btrieve description on page 1-29 and page
4-5 differ. Which is correct?
Answer:
Page 1-29 has a typographical error. Page 4-5 is
correct.
G. Do not load LSLENH or MSM31X in a NetWare 3.12
server (including RunTime).
H. If you have problems connecting, it may be a modem
problem. Try modem selections that are similar to
your modem. Also drop the baud rate. A useful
tool is to use a null modem cable and do a direct
connect to the NetWare Connect server.
I. If you use "Modem Independence," the modem strings
will be supplied by NetWare Connect instead of the
application:
1. If you use Modem Independence, inform the
application that the modem type is "Hayes
Compatible.
2. Expect a significant delay in the dialing.
The delay is caused by NetWare Connect
"translating" the initialization string.
3. Applications vary in their efficiency in
relating to Modem Independence. If you
experience problems with ports in a modem
independence group, disabling modem
independence may help.
J. Modems
1. If your modem is not included on the NetWare
Connect menu, do the following:
a) Download NWCMOD.EXE from NetWire in
NOVLIB, Library 9. NWCMOD.EXE adds
several new modems.
b) Try a similar modem; its initialization
string may fit your modem.
c) Do not expect the menu choice, "Hayes
Compatible," to provide anything better
than minimal performance.
d) If you want your modem added to the
list, FAX the manual pages that deal
with AT commands and Sregisters and
responses to Bob LoFaso at 408-747-4967.
e) Some US Robotics modems, outside of the
US, require a special initialization
string. If you are outside the US and
the supplied setting does not work,
please post a message in Section 2 of
NCONNECT on CompuServe.
2. The NetWare Connect modem scripts do not turn
on modem hardware compression. Instead, if
you have EMS memory, compression is performed
in the computers RAM. This should result in
a performance increase instead of a
reduction.
K. When using V.42 modems with NetWare Connect, you
may see a NCS incoming call processed by NetWare
Connect as an ARAS connection followed by the
phone hanging up.
This is caused because of a conflict between the
AppleTalk Remote Access 1.0 connection negotiation
and the modems V.42 negotiation.
Novell recommends doing one of the following
solutions:
1. Do not use the ARAS service of NetWare
Connect, and add an "Additional Modem
Initialization" string in the NetWare Connect
modem configuration field that enables modem
V.42 compression.
Note: If it is necessary to support ARAS
dial in users, choose solution 2.
2. Disable V.42 error control at the NCS client
side by appropriately configuring the NCS
application being used.
If this is not possible, define a unique set
of ports to be used for ARAP connections and
on all remaining ports, enable hardware V.42
compression in the modems through the NetWare
Connect modem configuration (as in solution
1).
II. NCS Connect Tips
A. Symptom:
The /NS parameter is provided for use with
applications that are aware of it and prepared to
take over the security role. No such applications
yet exist.
Solution:
For the present, do not use the /NS parameter.
However, if you want to decrease the amount of
security involved in LOGIN, see pages 9, 10, and
11 of the NetWare Connect Addendum.
B. Users calling in with a remote control application
must use a name and password that exist in the
bindery of the NetWare Connect server. Passwords
must consist of only alpha-numeric characters
without spaces.
C. The NCS service allows you to define both OutBound
and InBound port groups:
InBound Port Group (One per server)
t All ports in the InBound group will be
available to remote users calling in with
remote control applications (like ReachOut
and PC AnyWhere).
t All the ports in the InBound group will have
a single logical port name consisting of the
first eight characters of the NetWare Connect
server name plus "dialin."
For example, if the server name is
"Communications," the logical port name will
be COMMUNICDIALIN.
All workstations and application servers put
in the host mode must use that logical port
name.
t Attempting to dial out using the InBound
logical port name will cause an error.
OutBound Port Groups
t Use only ports that are in an OutBound group
for dialing out.
t OutBound Ports may be selected by group name
or individual name.
t If you select a port by group name, NetWare
Connect will select an available port within
the group.
t If you call out with an Int14 application,
use only a specific port name instead of a
group name.
t Unlike NASI, NINT14 does not release a port
until NINT14 is unloaded. NINT14 /U
InBound/OutBound Ports
t A port may be placed in both the InBound
group and one or more OutBound groups. This
allows InBound ports to be used for OutBound
calls except when a remote user is actually
connected.
D. If your application supports both NASI and Int14,
choose NASI when using NetWare Connect.
1. Few, if any, Int14 applications go faster
than 9,600 (at least not in this
environment.)
2. As described in the manual, NetWare Connect
supports only the basic Int14 features.
3. You must run NASI to be able to run Int14.
The reverse is not true.
E. A NASI.DLL file is available to any developer who
requests it. It will be of use to users only
after applications are developed with hooks for
it.
F. The only remote control applications that are
supported, through NCS, are the ones that support
NASI. They are usually identified as the "LAN
Version."
III. NRN Connect Tips
A. The frame type bound to RNS in the server must
match the frame type on the NRN client that will
be calling in to the server.
B. The NET.CFG file on the remote NRN client must
specify a preferred server for the shell to be
able to find a server. If the NetWare Connect
server is not RunTime, you should also the SET
REPLY TO GET NEAREST SERVER=ON parameter at the
server console.
C. When running NRN/Dialcon and MS Windows in
enhanced mode, serial port contention problems
will occur unless the SYSTEM.INI of the remote
workstation is modified to lock Windows out of the
port used by NetWare Connect.
Adding one of the following case sensitive lines
to the 386enh section of the SYSTEM.INI file
corrects the problem:
MaxComPort=0
Locks Windows out of all the remote
workstations serial ports.
COM1Irq=-1
Locks Windows out of port 1.
COM2Irq=-1
Locks Windows out of port 2.
D. If you will be using the servers comm ports,
AIOCOMX will report if it detects a 16550 UART.
(No report will be generated if a UART is not
detected.)
1. If it is a 16550 UART, you can safely operate
at up to 19,200 bps.
2. If you have not applied PTF436 (or PTF439 or
PTF442) and it is a 8250 UART or 16450 UART,
you should not try to operate at speeds over
2,400 bps.
3. If you have applied PTF436 and it is a 8250
or 16450, you can safely operate at up to
4,800 bps or, in many cases, up to 9,600 bps.
E. Before running TCP/IP and IPX over Remote Node, do
the following:
1. Edit the NWCSTART.NCF file and load RNS once
with the frame type of ethernet_II.
2. Bind IPX to RNS and also bind IP to RNS.
3. At the NRN workstation, edit the NET.CFG file
to use ethernet_II frame.
4. At this point, load the following files:
LSL.COM
NRN.COM
DIALCON.EXE
IPXODI.COM
TCPIP.EXE
NETX.EXE
LOGIN.EXE
You should now be logged into the NetWare
server and should be able to PING to any IP
host.
F. To run TCP/IP over remote node, you must specify
the node address for the driver in the NET.CFG
file. This statement should go in the Link Driver
NRN heading.
node address XXXXX
where XXXXX is a five digit hex node number.
G. On the Connect server, the subnet mask for all
adapters must be the same and the network
addresses must be unique (use the same rules you
would for any two or more adapters in the server).
H. Symptom:
User authentication fails in Dialcon.
Solution:
Ensure that the user name and password exists
in the bindery of the NetWare Connect server.
I. A workstation cannot run NRN until it logs out of
its local LAN. IPX will not bind to both the
serial driver and the network board.
J. Symptom:
(RNS/NRN) is unable to attach to a server using
NETX.
Solutions:
t Lower the Baud rate.
t Try a different modem selection and
definition.
t Try a different modem.
y